Method for managing commerce contexts

ABSTRACT

A method for managing commerce contexts between a direct commerce context and a temporary commerce context in a client session. Commerce context parameters are associated with the direct and temporary commerce contexts. The commerce context associated with a client request is determined according to the commerce context parameters associated with the client request.

CROSS REFERENCE TO RELATED APPLICATIONS

This Application claims priority under 35 U.S.C. §119(a) to CanadianPatent Application No. 2,432,616, filed Jun. 17, 2003, which is herebyincorporated herein by reference in its entirety.

TECHNICAL FIELD

The present invention relates to data processing systems, and moreparticularly to a context switch and a process for managing commercecontexts in client sessions.

BACKGROUND INFORMATION

Modern Internet and web applications commonly require information aboutthe user and user's activities to be maintained across multiplerequests. For example, in a typical online store, the user is providedwith a browseable catalog from which items can be selected and added toa shopping cart. Once the user has added all the desired items to theshopping cart, the user may proceed to the checkout where an order forthe items contained in the shopping cart may be placed. To accomplishthis process, multiple client requests are required and the informationfrom each request must be maintained across requests.

A hypertext transfer protocol (HTTP) is used to access many resources onthe Internet. However, HTTP is a stateless protocol that defines theformat of requests and corresponding responses but does not currentlydefine a mechanism for maintaining state information. In a typicalrequest, an HTTP user or client opens a connection with a server andrequests some information or a resource. The server responds with therequested resource, if available, or an HTTP error status page. Afterthe server's response, the connection is closed and the server does notmaintain any information about the client. Any subsequent request by theclient is considered a fresh request with no relation to the previousrequest.

Several approaches have been developed to maintain user informationacross requests and responses. These approaches use the notions ofsessions and states. A session is a series of HTTP requests originatingfrom the same client in the same browser instance or “working session.”State refers to information relating to the previous requests and otherbusiness decisions that may be made in relation to these requests.Utilizing these approaches, an Internet or web application should beable to associate a state with each session. Two common methods ofsession management are cookies and Universal Resource Locator (URL)rewriting. Cookies and URL rewriting are known in the art. Other sessionmanagement strategies are also known in the art. Generally, sessionmanagement strategies use an associated session area to storeinformation about the user session.

Many modern Internet and web applications are modular in design.Modularity allows different aspects of an application to be developedindependently from one another. The Model-View-Controller (MVC) designpattern is a common design paradigm used in developing modularapplications. The MVC design pattern is known in the art.

In many Internet and web applications, a user will typically have tonavigate through a number of organizations. These organizations may belocated in different domains. For example, in an electronic marketplaceor e-marketplace environment, a buyer in a supply channel may movebetween a manufacturer or supplier and distributors or resellers. Eachof these organizations is referred to as a store. Each store willtypically have its own commerce context, for example, a store context.Thus, when navigating between stores, it is necessary to manage theswitch between store contexts. A simple shopping flow illustrates thisproblem.

A typical shopping scenario for a supply channel may involve thefollowing steps:

-   -   (1) A buyer visits the channel store main page;    -   (2) Browses through the catalog;    -   (3) Places an order for a product;    -   (4) Receives a confirmation for the order;    -   (5) Continues browsing for other products.        The process steps described above may be given the following        names:    -   Step (1)—StoreFrontDisplay    -   Step (2)—ProductDisplay    -   Step (3)—OrderProcess    -   Step (4)—OrderDisplay    -   Step (5)—ProductDisplay

In this shopping scenario, the buyer moves back and forth between thechannel and a supplier store. In step (1), the StoreFrontDisplaydisplays the main page of the channel store. In step (2), ProductDisplayinvolves retrieving the product(s) from the catalog of the channel storeand rendering the product description(s). In step (3), OrderProcessinvolves placing the order in the supplier store. In step (4),OrderDisplay retrieves the order and displays the order. This step canbe performed in the channel store or the supplier store. In step (5)ProductDisplay, the buyer is in channel store browsing products from thecatalog.

To create a smooth shopping experience, there needs to be a way tomanage the switch between these store contexts. Several methods ofmanaging store contexts are known in the art. One method involvescreating a store identifier or store ID for each store, and appendingthe store ID as a parameter in each of the URLs that are called. TheURLs would look something like this for the process steps describedabove:

-   -   Step (1) . . . /StoreFrontDisplay?StoreID=c_store1    -   Step (2) . . . /ProductDisplay?StoreID=c_store1&ProductID= . . .    -   Step (3) . . . /OrderProcess?StoreID=s_store2 . . . .    -   Step (4) . . . /OrderDisplay?StoreID=s_store2    -   Step (5) . . . /ProductDisplay?StoreID=c_store1&ProductID= . . .        where c_store1 is the store ID for the channel store and        s_store2 is the store ID for the supplier store.

A disadvantage of this approach is that it requires web designers tohard code the store ID into URLs used in the Internet or webapplication. This additional complexity further complicates modularapplication design. For example, hard coding URLs in an MVC applicationmay affect the design of each of the model, view, and controllercomponents.

In view of these shortcomings, there exists a need for another method ofmanaging commerce contexts.

SUMMARY OF THE INVENTION

The present invention provides a method for managing commerce contextsusing direct and temporary commerce context parameters.

In accordance with one aspect of the present invention, there isprovided for a data processing system, a method for managing commercecontexts, the data processing system being associated with a directcommerce context and a temporary commerce context, the data processingsystem being operatively coupled to memory having a session area, themethod comprising the steps of receiving a client request associatedwith a commerce context parameter, and determining the commerce contextassociated with the commerce context parameter.

In accordance with another aspect of the present invention, there isprovided a computer program product having computer-readable mediumtangibly embodying code for directing a data processing system to managecommerce contexts, the data processing system being associated with adirect commerce context and a temporary commerce context, the dataprocessing system being operatively coupled to memory having a sessionarea, the computer program product comprising code for receiving aclient request associated with a commerce context parameter, and codefor determining the commerce context associated with the commercecontext parameter.

In accordance with a further aspect of the present invention, there isprovided a data processing system for managing commerce contexts, thedata processing system being associated with a direct commerce contextand a temporary commerce context, the data processing system beingoperatively coupled to memory having a session area, the data processingsystem comprising means for receiving a client request associated with acommerce context parameter, and means for determining the commercecontext associated with the commerce context parameter.

In accordance with yet a further aspect of the present invention, thereis provided a computer data signal embodied in a carrier wave and havingmeans in the computer data signal for directing a data processing systemto manage commerce contexts, the data processing system being associatedwith a direct commerce context and a temporary commerce context, thedata processing system being operatively coupled to memory having asession area, the computer data signal comprising a component in thecomputer data signal for receiving a client request associated with acommerce context parameter, and a component in the computer data signalfor determining the commerce context associated with the commercecontext parameter.

Other aspects and features of the present invention will become apparentto those ordinarily skilled in the art upon review of the followingdescription of specific embodiments of the invention in conjunction withthe accompanying figures.

BRIEF DESCRIPTION OF THE DRAWINGS

Reference will now be made to the accompanying drawings which show, byway of example, embodiments of the present invention, and in which:

FIG. 1 is a schematic diagram of a computer system suitable forpracticing the invention;

FIG. 2 is a schematic diagram of a server for the computer system ofFIG. 1 and which is connected to the computer system;

FIG. 3 is a block diagram of a data processing for the computer systemof FIG. 1;

FIG. 4 is a block diagram of one embodiment of a commerce context switchimplemented according to the present invention;

FIG. 5 is a schematic diagram of an electronic marketplace in which thepresent invention may be implemented;

FIG. 6 is a schematic diagram of one embodiment of a commerce contextswitch implemented according to the present invention;

FIG. 7 is a flowchart showing the steps in the operation of the commercecontext switch of FIG. 6;

FIG. 8 is a flowchart showing a process for handling commerce contextparameters by the commerce context switch of FIG. 6;

FIG. 9 is a flowchart of the procedure for determining the commercecontext at the end of a client request;

FIG. 10 is a flowchart of the procedure for determining the commercecontext in the session area at the end of a client request; and

FIG. 11 is a flowchart of a shopping scenario.

DETAILED DESCRIPTION OF THE EMBODIMENTS

The following detailed description of specific embodiments of thepresent invention does not limit the implementation of the invention toany particular computer programming language. The present invention maybe implemented in any computer programming language provided that theoperating system provides the facilities to support the requirements ofthe present invention. In one embodiment, the present invention isimplemented, at least partly, in the Java computer programming language.Any limitations presented herein as a result of a particular type ofoperating system or computer programming language are not intended aslimitations of the present invention.

Reference is first made to FIG. 1, which shows a computer system 20 uponwhich the present invention is implemented. The computer system 20includes a server 22 and clients 24 which are interconnected by anetwork 30. The server 22 may be modeled as a number of servercomponents including an application or business logic server, webserver, graphical user interface server, and a database server orresource manager. The clients 24 include computers, data processingsystems, handheld portable devices, or computer networks. The clients 24may be the same or different. In one embodiment, the network 30 is theInternet or World Wide Web (WWW). In such cases, the client devices areequipped with appropriate web browser software such as InternetExplorer™ from Microsoft Corporation or Netscape's Navigator™, and theapplication servers are equipped with appropriate HTTP server software,such as the WebSphere™ product from IBM.

The computer system 20 further includes resources 32 connected to thenetwork 30. The resources 32 include storage media, databases, forexample, a relational database such as the DB2™ product from IBM, a setof XML (extensible Markup Language) documents, a directory service suchas a LDAP (Lightweight Directory Access Protocol) server, and backendsystems. The interface between the server 22 and the resources 32comprises a local area network, Internet, or a proprietary interface.The resources 32 are accessed by the server 22 and the clients 24. Anyof the server 22, the clients 24, and the resources 32 may be locatedremotely from one another or may share a location. The configuration ofthe computer system 20 is not intended as a limitation of the presentinvention, as will be understood by those of ordinary skill in the artfrom a review of the following detailed description.

Referring now to FIG. 2, a server in the computer system 20 will bedescribed in more detail. The server 23 comprises a web applicationserver compliant with the Java Version 2 Enterprise Edition (J2EE)platform such as the WebSphere™ product from IBM. A client 25 connectsto the server 23 via the Internet or WWW. A user interface 26 ispresented to the client 25, using JavaServer Pages (JSPs) and servlets.Using JSP technology makes it easy for user interface developers topresent dynamically generated pages to any client equipped with anInternet browser. Servlets give more sophisticated developers ofJava-based applications the ability to implement dynamic presentationscompletely in the Java programming language. A business logic module 28is implemented on the server 23 using Enterprise JavaBean components(EJB) for the object layer. WebSphere™ and other J2EE-compliantapplication servers provide an organization that allows user interfacefunctions to be separated from the business logic module 28 on theapplication server 23. Those skilled in the art will recognize that manycomputing platforms, operating systems, and enterprise applicationserver suites may be used with the present invention without departingfrom the scope of the invention.

Referring now to FIG. 3, a data processing system 50 in the computersystem 20 is now described in more detail. The data processing system 50includes a processor 52, a memory 54, a display 56, and user inputdevices 58 such as a keyboard and a pointing device (e.g. mouse), and acommunication interface (not shown) for communicating with the network30 (FIG. 2). An operating system 60 and application programs 62, 64 runon the processor 52. The memory 54 includes random access memory (“RAM”)66, read only memory (“ROM”) 68, and hard disk 70. The data processingsystem 50 may be a client or a server.

Reference is now made to FIG. 4, which shows in a block diagram form animplementation for a commerce context switch 100 according to thepresent invention. The commerce context switch 100 is implemented infunctional modules in the form of computer software or a computerprogram product and executed by the processor 52 (FIG. 3) duringoperation of the computer program product. The commerce context switch100 is implemented in an application 101 and comprises a controllermodule 102, a model module 104, and a view module 106. A user interface105 allows a user to communicate with the controller module 102. Themodel module 104 is implemented using a Command pattern 103 thatoperates on Enterprise Java Beans.

The application 101 uses the MVC (Module-View-Controller) design patternto handle client requests and responses. The controller module 102determines which operation to perform and the proper execution contextfor each request based on the request parameters and session informationand data. This execution context is referred to as a command context.The command context is passed to the model 104 and the view 106 modules.

Referring still to FIG. 4, the controller module 102 communicates withthe user interface 105 by interpreting requests and handling responses.The model module 104 contains business logic operations and commands,and accesses data and other resources. The view module 106 handles thepresentation of information and data. In the operation of a webapplication, the controller module 102 interprets incoming HTTP requestsand invokes the requested business logic operation or command in themodel module 104. Upon completion of the business logic operation, thecontroller module 102 updates the view module 106. The controller module102 selects the next view to display based on the present data andresult of the operation of the business logic 28 (FIG. 2). Thecontroller module 102 then transmits the view to the user interface 105.

Some embodiments of the present invention may be implemented in adifferent application framework from that described below. Theapplication framework defines, at least in part, the order of events andoperations performed by the application. In one embodiment, theapplication framework may allow the client request to containinformation regarding the view to be invoked following the execution ofa command or business logic operation. In this case, following theexecution of the command, the controller module 102 invokes the nextview to be displayed based on the information in the client request.

Reference is now made to FIG. 5, which shows an implementation of anelectronic marketplace in which the present invention is operated. Ane-marketplace place is an electronic forum that brings multiple buyersand sellers together in a way that provides efficient electronic tradingof goods and services. An electronic marketplace or e-marketplace 201 isimplemented on a server 202. The e-marketplace environment may beprovided by a web application such as the WebSphere™ Commerce productfrom IBM. The e-marketplace 201 includes a direct store 203 having acatalog 204 and hosted supplier stores 206, indicated individually byreferences 206 a, 206 b, . . . 206 n. Stores hosted in this mannertypically have a hosted storefront served using the IT infrastructure ofthe direct or channel store 203 in the e-marketplace 201. Thee-marketplace 201 may also be operably connected to a remote supplierstore proxy server 208. The proxy server 208 is implemented on aseparate server or on the server 202. A user interface 210 permits aclient to connect with the server 202 and the e-marketplace 201. Theuser interface 210 provides an Internet or web browser with which aclient can navigate the e-marketplace 201. Non-hosted remote supplierstores 212, indicated individually by references 212 a, 212 b, . . . 212n, may connect to the e-marketplace 201 and the server 202 over theInternet 213 via the proxy server 208. Typically, the hosted stores 206are in the same domain as the channel store 203 and the non-hostedstores 212 are in a different domain.

Reference is now made to FIG. 6, which shows a system implementation ofa commerce context switch according to the present invention. A webbrowser 240 is used by a client in the e-marketplace 201 (FIG. 5). Thebrowser 240 may be used to display a web page 242 in the e-marketplace201 (FIG. 5) including buttons 244. The client may invoke an HTTPrequest using a command line invocation (not shown) in the browser 240or by clicking on one of the buttons 244 using a mouse or similarpointing device. A typical HTTP request may take the form:

http://<path>/<requestname>?<querystring>

where <path> is the URL, <requestname> are names which may identify, forexample, a business logic object or command to be performed in respectof the request, and <querystring> is query script in which queryparameters are typically separated by an “&”.

Referring back to FIG. 5, in the e-marketplace 201, a buyer may navigatethrough a number of organizations or stores during a shopping flow. Forexample, the buyer may visit a direct or channel store 203 integrating aplurality of the supplier stores 206 and 212. The catalog 204 may be anaggregation of the product offerings of the hosted stores 206 and theremote stores 212. In this arrangement, some of supplier stores coupledto the direct store 203 may be hosted while other stores may be remotelylocated. Similarly, some of the supplier stores may be in a differentdomain from the channel store 203. Typically, each store will have itsown commerce context, for example, a store context. A store may have itsown business logic and its own operational data. Similarly, the userexperience or “look and feel” of a store may be unique. For some stores,these and/or other aspects may be shared. A store context can containinformation such as the store supported language, currency, directoryfor web assets such as store pages, and various store policies.

When navigating between stores, it is necessary to manage the switchbetween store contexts. Typically, the client will switch between adirect or channel store context and supplier store contexts, for examplethe direct store 203 and a supplier store 206 (FIG. 5). Usually, theclient will return to the channel store after a transaction or event ina supplier store has been completed. For convenience, the channel storecontext is sometimes referred to as the direct store context, and thesupplier store context is sometimes referred to as the temporary storecontext. Store context parameters are used to manage the switch betweenstore contexts. Parameters StoreID and ForStoreID are used to identifythe channel store context and supplier store context respectively. Thechannel store context saved in the session is the Session StoreID.

In a typical scenario, a client visits a channel store 203. The StoreIDparameter is initially provided as a request parameter and stored in thesession as the Session StoreID on return. The client then browsesthrough other pages in the channel store 203 without specifying anyStoreID parameters on the subsequent requests. The client may then visita remote supplier store 212 in which case a ForStoreID parameter isused. When the client returns to the channel store 203 its StoreID isretrieved from the session and the proper store context is constructed.The command is aware of the StoreID but not its origin, e.g. whether theStoreID is derived from the request or the session area, or whether theStoreID refers to a direct store 203 or supplier store 206, 212.Similarly, the command does not know if a supplier store is a hostedstore 206 or a non-hosted remote store 212, e.g. in a different domainthan the channel store 203. This information is handled by the businesslogic 28 of the command using the StoreID.

Referring again to FIG. 6 and also the flowchart depicted in FIG. 7, thestore context parameters are explained in more detail. When a clientmakes an HTTP request in the browser 240, the controller module 102receives the request (step 302 in FIG. 7) and retrieves any requestparameters and session information and data (step 304 in FIG. 7). Thecontroller module 102 creates a command context 246 associated with therequest (step 306 in FIG. 7). The command context 246 is created freshfor each request and does not maintain information across requests. Inthis manner, the command context 246 is stateless. A command 248 isassociated with the client request and the command context 246. Thecommand 248 represents the client request, for example, the requestedbusiness logic operation. The command context 246 contains theinformation required to execute the command 248 such as the StoreID. Byway of example, a client may make the following HTTP request:

http://www.shoe.com/ProductDisplay?StoreID=203&ProductID=ABC

where “StoreID” and “ProductID” are request parameters and“ProductDisplay” represents the business logic command that is called bythe request.

The client request may contain one or more store context parameters, orno store context parameters. Table 1 shown below summarizes thecombinations of store context parameters that may be included in therequest. Using the request parameters and session information and data,the value of the StoreID to be stored in the command context 246 isdetermined (step 308 in FIG. 7).

A session area 250 provides a store for session data and informationincluding store context information and the Session StoreID. The sessionarea 250 persists across client requests. Session management isperformed using cookies, however other session management strategiessuch as URL rewriting may be used so long as the implemented solutionprovides a session area 250. Depending on the session managementsolution adopted, the session area 250 may be located on the clientdevice or the server.

The controller module 102 (FIG. 4) will construct a store context withthe StoreID in the command context 246 (step 310 in FIG. 7). Typically,the command context 246 will also contain some user information such aspreferences. Commands are used to implement business logic. Thecontroller module 102 (FIG. 4) determines the command to execute basedon the request name. Optionally, it can be based on the StoreID in thecommand context because we can have different business policies fordifferent store. Next the command 248 will execute using the commandcontext and the associated store context (step 312 in FIG. 7). Using thecommand result, a response is sent to the web browser 240 by thecontroller module 102 (step 314 in FIG. 7). In the case where theForStoreID request parameter is present, following execution of thecommand, the application 101 has the option of passing the commandcontext 246 to the view module 106 in its present state or changing theStoreID to the new session StoreID before passing it to the view. In thefirst case, the view will be displayed in the context of the ForStoreIDof the supplier store. In the second case, the view will be presented inthe context of the channel store. It should be noted that the frameworkof the present embodiment requires a store context parameter to beincluded in either the client request or the session area 250. If thesession area 250 does not contain a Session StoreID and the clientrequest does not include a StoreID or ForStoreID, the client requestwill fail and the client will be sent an HTTP error status page.

TABLE 1 Store Context Construction ForStoreID StoreID Store contextSession StoreID at parameter in parameter in StoreID in used in the theend of the request request Session command context request X ForStoreIDX X ForStoreID StoreID X StoreID StoreID X X StoreID StoreID X SessionStoreID Session StoreID X X ForStoreID Session StoreID X X X ForStoreIDStoreID

Referring now to FIG. 8, a process 319 for handling of the store contextparameters is described in more detail. In a first step 320, thecontroller module 102 (FIG. 4) receives an HTTP request. The controllermodule 102 (FIG. 4) operates using Java servlets. The controller module102 (FIG. 4) then retrieves the request parameters and session data(step 322). If the request contains a ForStoreID parameter (decisionblock 324), the controller module 102 (FIG. 4) stores the ForStoreIDparameter as the StoreID in the command context 246 (FIG. 6) (step 326).If a StoreID parameter is also present (decision block 327), the SessionStoreID will be set to the StoreID in the request (step 328). If noStoreID parameter is present, the Session StoreID will remain unchanged.

If no ForStoreID is present (decision block 324), the controller module102 (FIG. 4) determines if a StoreID is present (decision block 330). Ifa StoreID parameter is present, the controller module 102 (FIG. 4)stores the StoreID in the request as the StoreID in the command context246 (step 332). Next, the controller module 102 (FIG. 4) stores theStoreID as the Session StoreID in the session area 250 (step 334).

If no StoreID is present (decision block 330), the controller module 102(FIG. 4) stores the Session StoreID as the StoreID in the commandcontext 246 (step 336). If no Session StoreID is present (decision block335), this will be an error situation and the client will be sent anHTTP error status page (step 337).

Referring now to FIG. 9, a procedure 340 for determining the storecontext for the command context 246 is described in more detail. If theclient request contains a ForStoreID parameter (decision block 342), thecontroller module 102 (FIG. 4) stores the ForStoreID parameter as theStoreID in the command context 246 (step 344). In this case, the storecontext constructed is that of a supplier store.

If no ForStoreID is present (decision block 342), the controller module102 (FIG. 4) then determines if a StoreID is present (decision block346). If a StoreID parameter is present, the controller module 102 (FIG.4) stores the StoreID in the request in the command context 246 (step348). The store context is constructed based on the StoreID requestparameter. If no StoreID parameter is present (decision block 346) but aSession StoreID is present, the controller modules 102 (FIG. 4) storesthe Session StoreID in the command context 246 (step 349) and the storecontext is constructed based on the Session StoreID. If no SessionStoreID is present (decision block 345), this will be an error situationand the client will be sent an HTTP error status page (step 347).

Referring now to FIG. 10, a procedure 359 for determining the storecontext in the session area 250 at the end of the request will beexplained in more detail. If a StoreID parameter is present in theclient request (decision block 360), the Session StoreID will be changedto the StoreID at the end of the request processing (step 362). If noStoreID is present in the request, the Session StoreID at the end of therequest processing will be the Session StoreID currently in the sessionarea 250.

Reference is next made to FIG. 11, which illustrates the steps for anexemplary shopping scenario in the e-marketplace 201 in accordance withthe present invention. As in many online stores, clients are providedwith a browseable product catalog 204 (FIG. 5) from which items can beviewed. In this example, the client has opened a new session in the webbrowser 240 (FIG. 6). In a first step 402, the buyer visits the mainpage of a channel store 203 integrating a plurality of supplier storeswhich may be located locally or remotely. The URL for this action mayappear as follows:

http://www.onlinestores.com/StoreFrontDisplay?StoreID=203

Because this is a new session, there is no StoreID in the session area250 (FIG. 6). The controller module 102 (FIG. 4) retrieves the StoreIDparameter from the request and stores it in the command context 246(FIG. 6). The store context is then constructed based on the StoreID andthe StoreFrontDisplay command is executed. The resultant storefront viewis generated and sent to the web browser 240 (FIG. 6). The SessionStoreID is then set to the StoreID. The Session StoreID is now apersistent global variable available in the session.

The buyer may then browse the catalog 204 (FIG. 5) for products toorder. Next in step 404, the buyer selects a product to be displayed.The URL for this action may appear as follows:

http://www.onlinestores.com/ProductDisplay?ProductID=ABC1

where ProductID is a parameter identifying a product. The controllermodule 102 (FIG. 4) retrieves the ProductID parameter from the request.The client request does not include a StoreID so the controller module102 (FIG. 4) retrieves the Session StoreID from the session area 250(FIG. 6) and stores it as the StoreID in the command context 246 (FIG.6). The store context is then constructed using the StoreID and theProductDisplay command is executed. The resultant product display viewis then generated and sent to the web browser 240 (FIG. 6).

Next in step 406, the buyer chooses to order the product “ABC1”. Thisproduct belongs to supplier store “20”. The URL for this action mayappear as follows:

http://www.onlinestores.com/OrderProcess?ForStoreID=20&ProductID=ABC1

In this case, a ForStoreID is present so the OrderProcess command willbe executed in a supplier store context rather than the channel storecontext. The controller module 102 (FIG. 4) retrieves the ForStoreIDparameter from the request and stores it as the StoreID in the commandcontext 246 (FIG. 6). The store context is then constructed using theStoreID and the OrderProcess command is executed. The resultant view isthen generated and sent to the web browser 240 (FIG. 6).

Next in step 408, an order confirmation is displayed. The URL for thisaction may appear as follows:

http://www.onlinestores.com/OrderDisplay?ForStoreID=20&ProductID=ABC1

The controller module 102 (FIG. 4) retrieves the ForStoreID parameterfrom the request and stores it as the StoreID in the command context 246(FIG. 6). The store context is then constructed using the StoreID andthe OrderDisplay command is executed. The resultant view is thengenerated and sent to the web browser 240 (FIG. 6).

Next in step 410, the buyer is returned to browsing in the catalog 204(FIG. 5). The URL for this action may appear as follows:

http://www.onlinestores.com/ProductDisplay?ProductID=ABC1

The controller module 102 (FIG. 4) retrieves the ProductID parameterfrom the request. Because there is no store context parameter specifiedin the request, the controller module 102 (FIG. 4) retrieves the SessionStoreID from the session area 250 (FIG. 6) and stores it as the StoreIDin the command context 246 (FIG. 6). The store context is thenconstructed using the Session StoreID and the ProductDisplay command isexecuted. The resultant product display view is then generated and sentto the web browser 240 (FIG. 6).

It will be appreciated by one of ordinary skill in the art thatapplication frameworks different from that described above may be usedwithout departing from the scope of the present invention. For example,in another framework, a login operation may be performed prior to theStoreFrontDisplay operation. This login operation may store the StoreIDparameter in the session area 250 prior to the step of displaying therequested storefront. Allowance for variation in the framework permitsmore customizable application design. For example, after the completionof an event, designers may choose to display an order confirmationwhich, may be performed in the supplier store or channel store, or theclient may be returned to browsing the catalog in the channel store.Also, depending on the application framework implemented, some commandparameters, for example the view parameters, may be included in the HTTPrequest or hard coded into the business logic of the command. It willalso be appreciated by one of ordinary skill in the art that the methodof managing store contexts provided by the present invention may be usedfor other e-marketplace operations, for example, a request forquotations (RFQ). Further, the present invention may be used to manageother commerce information that requires a temporary switch such aslocale, language or currency information.

The present invention may be embodied in other specific forms withoutdeparting from the spirit or essential characteristics thereof. Certainadaptations and modifications of the invention will be obvious to thoseskilled in the art. Therefore, the presently discussed embodiments areconsidered to be illustrative and not restrictive, the scope of theinvention being indicated by the appended claims rather than theforegoing description, and all changes which come within the meaning andrange of equivalency of the claims are therefore intended to be embracedtherein.

1. For a data processing system, a method for managing commercecontexts, the data processing system being associated with a directcommerce context and a temporary commerce context, the data processingsystem being operatively coupled to memory having a session area, saidmethod comprising the steps of: receiving a client request associatedwith a commerce context parameter; determining the commerce contextassociated with said commerce context parameter; and constructing thecommerce context associated with said commerce context parameter,wherein said client request further includes a second commerce contextparameter, and wherein said method further comprises the step ofdefining said second commerce context parameter in the session area. 2.The method as claimed in claim 1, wherein the step of determining thecommerce context associated with said commerce context parameterincludes determining whether said commerce context parameter identifiessaid direct commerce context or said temporary commerce context.
 3. Themethod as claimed in claim 1, wherein said commerce context parameter isincluded in said client request.
 4. The method as claimed in claim 1,wherein said commerce context parameter is defined in the session area.5. The method as claimed in claim 1, further comprising the step ofexecuting said client request using said constructed commerce context.